| Author | Thread Statistics | Show CCP posts - 5 post(s) | 
      
      
        |  Max Kolonko
 High Voltage Industries
 Ash Alliance
 
 381
 
 
       | Posted - 2014.03.23 22:50:00 -
          [1] - Quote 
 I like the notion to delay signals of K162 on the overlay and passive ship scanner
 
 But i dont like the idea of delaying it on probes. if a farming fleet commits one or more people to scanning duty they should be able to get information faster that just by staring ot the passive scan results.
 
 Right now you get the info for free, with new system you will have to do some work to get it in time to safe your fleet / call in reinforcments.
 
 The end goal for the change is to get more fights, but is it more fights that will be given or just more ganks? If somoene will not place probers on watch they are stupid but if they doo, they should have an edge. even if slight. compared to the overlay.
 Read and support:
 Don't mess with OUR WH's
 What is Your stance on WH stuff?
 | 
      
      
        |  Max Kolonko
 High Voltage Industries
 Ash Alliance
 
 381
 
 
       | Posted - 2014.03.24 00:06:00 -
          [2] - Quote 
 
 Derath Ellecon wrote:Sephira Galamore wrote:Derath Ellecon wrote:And Mynnna, please keep your nose out of areas you have no understanding. A WH "ESS" is just a total BS idea given the nature of WH income to begin with. The idea isn't _that_ bad tbh.  You could explain it along the lines of.. "WH effects prevent the use of normal tractor devices" or something..  No it is bad. There is a major difference between WH income and 0.0 income. If I get jumped in a Sanctum, I at least got bounties paid for all of my activity up until that point. (whatever the % is based on an ESS etc). In WH space I make 0 isk running WH sites. (risk involved). In fact I make 0 isk collecting loot and salvaging (risk involved). In fact in order to make ANY isk I have to: 1. Run a site 2. Loot salvage a site 3. Safely store the loot (there is a risk however small of getting evicted) 4. Transport the loot through WH space 5. transport the loot thru k-space to a station for sale. each step of the way has enough risk just to make the isk.  So no WH ESS is bad. Turn the blue loot into bounties maybe, but otherwise no. 
 
 and 3.5 - spy can steal it
 
 
 besides, killing farming fleet on site is not about getting their isk, is about getting the kills themself, who cares if i grab their loot or not if i kill their triage and dreads in the process
 Read and support:
 Don't mess with OUR WH's
 What is Your stance on WH stuff?
 | 
      
      
        |  Max Kolonko
 High Voltage Industries
 Ash Alliance
 
 381
 
 
       | Posted - 2014.03.24 00:07:00 -
          [3] - Quote 
 
 Kateryna I wrote:Quincy Thibaud wrote:This is good. I approve. 
 While you're at it, how about making ships that enter a null or low sec system from a WH in that system have a delayed appearance in local?
 
 
 This, definitely would need to go in line with the fix. Also scaling the delay ie. C1 no delay, C6 big delay. Also mass dependant, ie one frig goes through and sig is still not visible for x time depending on WH class,three cruisers go through and it immediately shows up, again mass and time delay dependant on WH class. There are some things this change can improve, but it will be all in the details as to not to spoil the fun for either groups of players. 
 the moment the fleet jumped trough wh its already too late for defender
 Read and support:
 Don't mess with OUR WH's
 What is Your stance on WH stuff?
 | 
      
      
        |  Max Kolonko
 High Voltage Industries
 Ash Alliance
 
 381
 
 
       | Posted - 2014.03.24 00:12:00 -
          [4] - Quote 
 
 Intana Kreis wrote:I doubt if any of the complicated mechanisms a lot of players outlined above have a hope of ever being implemented. It'll turn out that a wormhole is actually a special case of some other object, doesn't have any of the properties needed to implement the necessary statistics, and adding in all the dependencies would be half a POS-rewrite worth of code. 
 
 who said it will be wh specific? I'm pretty sure it will work for ALL k162 in the game and not only in wh
 Read and support:
 Don't mess with OUR WH's
 What is Your stance on WH stuff?
 | 
      
      
        |  Max Kolonko
 High Voltage Industries
 Ash Alliance
 
 381
 
 
       | Posted - 2014.03.24 00:17:00 -
          [5] - Quote 
 
 Karen Galeo wrote:Right, lots of thoughts in this thread already. One of my favorites: Quote:And that just re-emphasizes how "you can't get this intel no matter what you do" is a problem. I absolutely think that the new sigs should not show up on the overlay, and I would be fine with a 30 - 45 second delay before the K162 is probable - time for the scout who scanned down the named side to warp to it, jump through, and hold their cloak. Any longer than that (the aforementioned 5 mins +/- 2 that someone brought up, or the 15 min someone said, or the 20 minutes it'd take for the sig to propagate at .1 AU/s across a 120 AU system) and things tilt far too far in favor of the people who opened the hole. This will affect more than just the 'targeted' cap escalation fleets - especially if the delay is higher (!) for a bigger threat, like a larger hole. 
 
 i kind of agree that defenders indeed have few extra secionds due to warp time and jump time scanner have to perform.
 
 But i would take no more than 20 seconds into consideration (if the goal is to just balance the time scanner need to actually appear in system)
 
 Covert ops (t3 are in disadvantage here) need less than 10 sec to land on wh (unless huge system) and another 5 -10 seconds to load new system after clicking jump. period. t3's need few more seconds of warp. so in avarage from the moment scaner calls warp to the moment he is in the system its 20 secs, give or take 5 sec.
 Read and support:
 Don't mess with OUR WH's
 What is Your stance on WH stuff?
 | 
      
      
        |  Max Kolonko
 High Voltage Industries
 Ash Alliance
 
 381
 
 
       | Posted - 2014.03.24 00:20:00 -
          [6] - Quote 
 
 Derath Ellecon wrote:Max Kolonko wrote:besides, killing farming fleet on site is not about getting their isk, is about getting the kills themself, who cares if i grab their loot or not if i kill their triage and dreads in the process And here lies one telltale issue. Something like this is going to make it far more dangerous to make isk in WH space. That being said while WH income is good, it really doesn't get "great" until C5+ C1-C4 income can get pretty decent, but when you factor in all of the "extra" stuff the isk/hr really isn't amazing. You have the logistics/cost of a POS. You have the logistics of getting loot to market, manually splitting isk between members (since it isn't bounty based). You have lots of static rolling to hope to keep isk flowing vs respawning 0.0 anoms and unlimited missions. Bottom line is something this drastic will likely empty out much of C1-C4 space. I roam around a fair amount and it is already empty enough. I want more groups to come live in WH space, not fewer. What I still don't get is what is the goal? I don't recall people really complaining hard about this issue until the overlay came about. So fix the overlay issue. Either disable it in WH space or make it scan at such a low frequency it is not viable as a passive intel tool. Why is there suddenly a need to swing the pendulum farther? 
 exactly - the overlay is the problem, so i think the overlay - at least for k162 - should be delayed (no need for delaying other sugnals as they are not imidiate threat that attacker can exploit) but leave probes as they are right now.
 Read and support:
 Don't mess with OUR WH's
 What is Your stance on WH stuff?
 | 
      
        |  |  |